* feat: Add Pod Disruption Budget support to Helm chart (apache#2380)

* chore(deps): update quay.io/keycloak/keycloak docker tag to v26.3.3 (apache#2407)

* Mention Helm chart support for PodDisruptionBudget in CHANGELOG.md (apache#2408)

* chore: Suppress javac deprecation warnings in SparkCatalog (apache#2394)

SparkCatalog intentionally overrides and uses deprecated
methods from Spark's TableCatalog.

This PR adds suppression annotations to allow for clean
compilation given that the deprecated method calls and
overrides are clearly expected in this case.

* Python client auto generate (apache#2192)

* Python client auto generate

* Python client auto generate

* Python client auto generate

* Python client auto generate

* Python client auto generate

* Python client auto generate

* Remove auto generated doc

* undo

* Fix doc

* Fix docker ref from CONTAINER_TOOL to DOCKER

* Add client help manual to GH action

* Add missing region to MinIO getting-started example (apache#2411)

The example was missing an AWS region, thus causing Spark to fail with:

```
spark-sql ()> create table ns.t1 as select 'abc';
25/08/20 16:25:06 ERROR Executor: Exception in task 0.0 in stage 0.0 (TID 0)
software.amazon.awssdk.core.exception.SdkClientException: Unable to load region from any of the providers in the chain software.amazon.awssdk.regions.providers.DefaultAwsRegionProviderChain@47578c86: [software.amazon.awssdk.regions.providers.SystemSettingsRegionProvider@1656f847: Unable to load region from system settings. Region must be specified either via environment variable (AWS_REGION) or  system property (aws.region)., software.amazon.awssdk.regions.providers.AwsProfileRegionProvider@2bbaabe3: No region provided in profile: default, software.amazon.awssdk.regions.providers.InstanceProfileRegionProvider@54b1cfd8: Unable to contact EC2 metadata service.]
...
        at org.apache.iceberg.aws.AwsClientFactories$DefaultAwsClientFactory.s3(AwsClientFactories.java:119)
        at org.apache.iceberg.aws.s3.S3FileIO.client(S3FileIO.java:391)
        at org.apache.iceberg.aws.s3.S3FileIO.newOutputFile(S3FileIO.java:193)
```

* Add feature config to allow dropping views without purging (apache#2369)

* Add feature config to allow dropping views without purging

With tables, the client can decide whether to purge the table
on drop or not. However, Polaris Servers used to unconditionally
perform the purge on dropping a view.

After apache#1619 that behaviour effectively prevents dropping views
if the admin user does not set `DROP_WITH_PURGE_ENABLED`. The
latter, though, is not currently advisable per apache#1617.

This change introduces a new feature configuration
(`PURGE_VIEWS_ON_DROP`) that allows the admin user to instruct
Polaris servers to drop views without purging to achieve
operational parity with tables.

Fixes apache#2367

* review: rename to PURGE_VIEW_METADATA_ON_DROP

* review: re-fix description

* Last merged commit c97b150

---------

Co-authored-by: Bryan Maloyer <bryan.mlyr@gmail.com>
Co-authored-by: Mend Renovate <bot@renovateapp.com>
Co-authored-by: Alexandre Dutra <adutra@apache.org>
Co-authored-by: Dmitri Bourlatchkov <dmitri.bourlatchkov@gmail.com>
Co-authored-by: Yong Zheng <yongzheng0809@gmail.com>